Skip to content

fix(implementation): define wave unit; one writer per worktree under worker authority (#4262) - #4698

Merged
cursor[bot] merged 5 commits into
mainfrom
cursor/4262-wave-unit-one-writer-37e9
Sep 27, 2026
Merged

cursor[bot] merged 5 commits into
mainfrom
cursor/4262-wave-unit-one-writer-37e9

Conversation

@kyle-sexton

Copy link
Copy Markdown
Contributor

Fixes #4262

Summary

Defines a wave as one phase’s worker-row batch. One git writer per worktree binds under both commit authorities (worker → serialize shared worktree; concurrent shared worktree needs orchestrator). Keeps #4511 orchestrator concurrency. New/updated evals 7 and 9.

Versions: implementation → 0.18.2; work-items wording bump (may collide with stacked #4688–#4690 — serialize on merge).

Sources

  • git-worktree / lockfile.h; triage A+B outcome B

Test plan

  • evals; changelog parity (per implementer)

Notes

Merge after work-items stack #4688/#4689/#4690 if those land first, or renumber work-items here.

Open in Web Open in Cursor 

cursoragent and others added 3 commits September 27, 2026 21:39
… per worktree under both commit authorities (#4262)

A wave is a batch of one phase's worker rows, each an independent brief
with its own disjoint fence; --wave-cap bounds rows in flight. The
single-committer rule #4511 shipped bound only under orchestrator
authority; under the default worker authority rows sharing a worktree
now run one at a time, and concurrent rows in a shared worktree need
orchestrator. Updates the wave-cap eval and adds a worker-authority
shared-worktree eval.

Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
…bounds (#4262)

The userConfig description, README, and work skill said the cap bounds
"concurrent dispatch waves"; it bounds the worker rows of one phase
implement-dispatch runs at once, one wave.

Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
# Conflicts:
#	plugins/implementation/.claude-plugin/plugin.json
#	plugins/implementation/CHANGELOG.md
#	plugins/implementation/skills/implement-dispatch/SKILL.md

Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
@cursor
cursor Bot marked this pull request as ready for review September 27, 2026 22:09
@github-actions

Copy link
Copy Markdown
Contributor

PR body contract — issue linkage

This PR body does not yet satisfy the issue-linkage contract:

  • Missing a "## Fix" section. State the concrete change and how it addresses the problem.
  • Missing a "## Verification" section. Record concrete evidence the change works (commands, gates, output).
  • Missing a "## Related" section. List related PRs, ADRs, or decision-log entries this PR does not close.

Edit the body and this comment updates itself on the next run.

cursoragent and others added 2 commits September 27, 2026 22:54
Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
Co-authored-by: Kyle Sexton <kyle-sexton@users.noreply.github.com>
@cursor
cursor Bot merged commit d65796c into main Sep 27, 2026
15 checks passed
@cursor
cursor Bot deleted the cursor/4262-wave-unit-one-writer-37e9 branch September 27, 2026 23:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

implement-dispatch's --wave-cap caps a concurrency unit the skill never defines, and there is no single-committer protocol

2 participants